-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add docs for releasing Phoenix assets #3186
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
a6c42fc
to
af5cf92
Compare
docs/releasing.md
Outdated
4. Update the go module `ocis-pkg` to the latest version <https://blog.golang.org/using-go-modules> . | ||
5. Update the phoenix asset in the Makefile. | ||
6. Run `go generate`. | ||
7. Create Changelog item for the Update in the `$major.$minor.$patchVersion_YYYY-MM-DD` folder. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
make generate
@PVince81 @LukasHirt This is laying around some time now. Can you give Feedback? |
Looks nice, just thinking though if the docs is the right place for this. Since the releases will be anyway done by the team and it's more a process then maybe would handbook be a better location? ^ Not saying it should be like that, just asking 😉 |
docs/releasing.md
Outdated
3. Move all changelog items from the `changelog/unreleased/` folder to the `$major.$minor.$patchVersion_YYYY-MM-DD` folder. | ||
4. Commit your changes. | ||
5. After merging, wait for the CI to run on the merge commit. | ||
6. Go to "Releases" in GH click "Draft a new Release". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing "and" before click?
docs/releasing.md
Outdated
2. Create a Folder in `changelog` for the release version and date `mkdir $major.$minor.$patchVersion_YYYY-MM-DD`. | ||
3. Move all changelog items from the `changelog/unreleased/` folder to the `$major.$minor.$patchVersion_YYYY-MM-DD` folder. | ||
4. Update the go module `ocis-pkg` to the latest version <https://blog.golang.org/using-go-modules> . | ||
5. Update the phoenix asset in the Makefile. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how ?
docs/releasing.md
Outdated
1. Create a branch `release-$version`. in <https://github.com/owncloud/ocis-phoenix> | ||
2. Create a Folder in `changelog` for the release version and date `mkdir $major.$minor.$patchVersion_YYYY-MM-DD`. | ||
3. Move all changelog items from the `changelog/unreleased/` folder to the `$major.$minor.$patchVersion_YYYY-MM-DD` folder. | ||
4. Update the go module `ocis-pkg` to the latest version <https://blog.golang.org/using-go-modules> . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how ? add the command directly
@micbar can we move this to the repo ocis-phoenix ? we could still link to that page from here I can take care if you agree |
to clarify: we keep the Phoenix repo related docs here in this PR but move the ocis-phoenix ones to the other repo and link them together |
I've extracted the ocis-phoenix bit into owncloud/ocis-phoenix#71 next up: reducing this PR to the minimum needed for a Phoenix release |
af5cf92
to
a0ccb3c
Compare
rebased and adjusted, please review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist:
Open tasks: